-
Notifications
You must be signed in to change notification settings - Fork 519
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: pgbouncer for postgresql #1607
Conversation
an example for feature request: #1604 I will cleanup this and make proper tests if accepted. |
@shcherbak i tested
get pods
other checks
|
It is not enabled by default
сб, 23 лист. 2024 р. о 13:15 Anton Patsev ***@***.***> пише:
… @shcherbak <https://github.com/shcherbak> i tested
helm install -n test --wait sentry . --values values.yaml --timeout=1000s
get pods
k get pod -n test
NAME READY STATUS RESTARTS AGE
sentry-billing-metrics-consumer-7fdf59945f-rcccz 1/1 Running 0 26m
sentry-clickhouse-0 1/1 Running 0 38m
sentry-cron-7c76c944bd-gsmsk 1/1 Running 2 (37m ago) 38m
sentry-generic-metrics-consumer-7d54df5775-btvgs 1/1 Running 0 26m
sentry-ingest-consumer-attachments-8d948fc4c-vwrhx 1/1 Running 0 26m
sentry-ingest-consumer-events-68d56779f6-r2bz2 1/1 Running 0 26m
sentry-ingest-consumer-transactions-6649b4ccdd-h6xjs 1/1 Running 0 26m
sentry-ingest-monitors-78c4f7965f-lxctv 1/1 Running 0 26m
sentry-ingest-occurrences-5969495499-qtzq2 1/1 Running 0 26m
sentry-ingest-replay-recordings-6c84bcf-p775z 1/1 Running 0 26m
sentry-issue-occurrence-consumer-5db94d5658-866hq 1/1 Running 0 25m
sentry-kafka-controller-0 1/1 Running 0 38m
sentry-kafka-controller-1 1/1 Running 0 38m
sentry-kafka-controller-2 1/1 Running 0 38m
sentry-metrics-consumer-5dccb9ff99-g5m6p 1/1 Running 0 26m
sentry-nginx-78665d4559-hf5wx 1/1 Running 0 38m
sentry-post-process-forward-errors-549f7f79b-ls2sx 1/1 Running 0 26m
sentry-post-process-forward-issue-platform-cb64b9d79-7xc69 1/1 Running 0 26m
sentry-post-process-forward-transactions-84598f8955-8lj89 1/1 Running 0 26m
sentry-rabbitmq-0 1/1 Running 0 38m
sentry-relay-67b8c8fdd7-r9lzr 1/1 Running 0 25m
sentry-sentry-postgresql-0 1/1 Running 0 38m
sentry-sentry-redis-master-0 1/1 Running 0 38m
sentry-sentry-redis-replicas-0 1/1 Running 0 38m
sentry-snuba-api-7c4477f94f-ghtmj 1/1 Running 0 38m
sentry-snuba-consumer-5f58b45676-9x552 1/1 Running 0 26m
sentry-snuba-generic-metrics-counters-consumer-5958fdbdfb-bx9l9 1/1 Running 0 26m
sentry-snuba-generic-metrics-distributions-consumer-6b9f5bd6zfd 1/1 Running 0 26m
sentry-snuba-generic-metrics-sets-consumer-64dcbcf556-rfhg2 1/1 Running 0 26m
sentry-snuba-group-attributes-consumer-5499c88f78-k4ftf 1/1 Running 0 26m
sentry-snuba-metrics-consumer-85b94f67b5-sbxm9 1/1 Running 0 26m
sentry-snuba-outcomes-billing-consumer-648bb8db8c-fxrkz 1/1 Running 0 26m
sentry-snuba-outcomes-consumer-6f87949797-sz2jq 1/1 Running 0 25m
sentry-snuba-replacer-6d4c8d987-9qlsn 1/1 Running 0 25m
sentry-snuba-replays-consumer-766d8f46f9-xn4t5 1/1 Running 0 26m
sentry-snuba-spans-consumer-7d8c4c88bb-kdf9n 1/1 Running 0 26m
sentry-snuba-subscription-consumer-events-8657877bf4-swcn6 1/1 Running 0 25m
sentry-snuba-subscription-consumer-metrics-5bb7875c8f-4tvtm 1/1 Running 0 25m
sentry-snuba-subscription-consumer-transactions-5c96cbf458b77p4 1/1 Running 0 25m
sentry-snuba-transactions-consumer-5bc869f55b-h7d9s 1/1 Running 0 26m
sentry-subscription-consumer-events-758dd79459-nzj6p 1/1 Running 0 26m
sentry-subscription-consumer-generic-metrics-b78474bb4-dtx2t 1/1 Running 0 26m
sentry-subscription-consumer-metrics-7b7f7b7dcb-2857d 1/1 Running 0 26m
sentry-subscription-consumer-transactions-7c99cf6c67-drslm 1/1 Running 0 26m
sentry-web-5d8cb8c964-t44nt 1/1 Running 1 (37m ago) 38m
sentry-worker-84fbbb4bf-5chmb 1/1 Running 2 (37m ago) 38m
sentry-zookeeper-clickhouse-0 1/1 Running 0 38m
other checks
k get pod -A | grep pgbouncer
empty
k get deploy -A | grep pgbouncer
empty
—
Reply to this email directly, view it on GitHub
<#1607 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ADNTAAH3K2MQGEMOX2HTDML2CBPUBAVCNFSM6AAAAABSKJHJDGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIOJVGQ2DGNBRGA>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
@shcherbak I have enabled the installation of pgbouncer |
there was a typo in enabler value name |
there is work to be done with pgbouncer chart: additional envs, proper port configuration. maybe pgbouncer should be enabled by default. after enabling pgbouncer my sentry setup with HPA started using for 30% less resources. and i want to use this feature from main stream chart |
values.yaml
log pgbouncer
k get pod -n test
|
fixed typo: POSTGRES_PASSWORD -> POSTGRESQL_PASSWORD |
this version of chart is deployed on my cluster with pgbouncer enabled |
work
k get pod -n test
|
@Mokto @patsevanton Is it ready to merge? Or there more to do? |
You can deploy postgres and pgbouncer yourself and specify the connection via pgbouncer in externalPostgres values section. Why add this to the chart? |
@adonskoy because pgpouncer is the single correct option to use postgres with workloads under autoscaling control |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks!
No description provided.